This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@cloudflare/[email protected]

Minor Changes

• #8080 d0fda3d Thanks @jamesopstad! - No longer call next in server middleware.

  This is so that the Cloudflare plugin can override subsequent dev middleware for framework integrations.

Patch Changes

• #8079 1b07419 Thanks @jamesopstad! - Call writeDeployConfig in writeBundle rather than builder.buildApp.

  The deploy config file is now written in the writeBundle hook rather than builder.buildApp. This ensures that the file is still written if other plugins override builder in the Vite config.

• Updated dependencies [3fb801f, fff677e, 3fb801f, 542c6ea, 3fb801f, 4db1fb5, 542c6ea, 1bc60d7, 1aa2a91, 35710e5]:

  • [email protected]
  • [email protected]
  • @cloudflare/[email protected]

[email protected]

Minor Changes

• #8120 3fb801f Thanks @sdnts! - Add a new update subcommand for Queues to allow updating Queue settings

• #8120 3fb801f Thanks @sdnts! - Allow overriding message retention duration when creating Queues

• #8026 542c6ea Thanks @penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

  This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API

• #8026 542c6ea Thanks @penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

  This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

  Advanced usage:

  • --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
  • --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/

Patch Changes

• #8112 fff677e Thanks @penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata

• #8120 3fb801f Thanks @sdnts! - Check bounds when overriding delivery delay when creating Queues

• #7950 4db1fb5 Thanks @cmackenzie1! - Add local binding support for Worker Pipelines

• #8119 1bc60d7 Thanks @penalosa! - Output correct config format from wrangler d1 create. Previously, this command would always output TOML, regardless of the config file format

• #8130 1aa2a91 Thanks @emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetry

  User provided strings are still left redacted as always.

• #8061 35710e5 Thanks @emily-shen! - fix: respect WRANGLER_LOG in wrangler dev

  Previously, --log-level=debug was the only way to see debug logs in wrangler dev, which was unlike all other commands.

• Updated dependencies [4db1fb5]:

  • [email protected]

[email protected]

Patch Changes

• #7950 4db1fb5 Thanks @cmackenzie1! - Add local binding support for Worker Pipelines

@cloudflare/[email protected]

Patch Changes

• Updated dependencies [4db1fb5]:
  • [email protected]

@cloudflare/[email protected]

Patch Changes

• Updated dependencies [3fb801f, fff677e, 3fb801f, 542c6ea, 3fb801f, 4db1fb5, 542c6ea, 1bc60d7, 1aa2a91, 35710e5]:
  • [email protected]
  • [email protected]

@cloudflare/[email protected]

Patch Changes

• #8116 ee4873c Thanks @WillTaylorDev! - Adds a RewriteFrames integration for workers-shared Sentry source-mappings.

• #8122 e8829e3 Thanks @GregBrimble! - fix: interpolation search method now checks for a single match at the beginning of every iteration

• #8115 dba3f21 Thanks @GregBrimble! - chore: Bump interpolation search method for asset manifest reading to 1%

• #8117 08e37f6 Thanks @WalshyDev! - Change asset-worker and router-worker analytics to using version tag rather than version UUID.

• #8126 59eda4a Thanks @GregBrimble! - chore: Add status code analytics to router-worker

• #8105 f2e6e74 Thanks @GregBrimble! - fix: Handles a divide by zero error that could occur when searching large manifests

• #8127 d4d5987 Thanks @GregBrimble! - chore: Bump interpoplation search method for asset manifest reads to 50%